traffic-type ipip
	 
   
  Configures the ipip header type to be
		matched for traffic classification.
 Syntax
			 
	 traffic-type ipip
				ip
					[
					A.B.C.D
					|
					X:X::X:X
					|
					any
					]
			
			traffic-type ipip
				mode
					[
					decap
					|
					new-scope
					]
			
		no
				traffic-type ipip
			[
				ip
				|
				mode
				]
 
	 Parameters
			
			
				
					- ipip
					
- Specifies the ipip header to
						be matched for classifying the packet.
- ip
					
- Specifies the actions for
						matching packets.
							
								- A.B.C.D
- Specifies the
									IPv4 address.
- X:X::X:X
- Specifies the
									IPv6 address.
- any
- Specifies any
									source IP address.
 
- mode
					
- Specifies the actions for
						matching packets.
							
								- decap
- Removes the
									encapsulated header.
- new-scope
- Shifts the scope
									of headers to inner headers for further processing.
 
Modes
			
			Ingress-group config
                                mode
		
 
	 Usage Guidelines
			
			Validations for the command are as follows:
			
				- This command is available only to users with the admin
                                        role.
- Valid decapsulation type and
                                        corresponding ID must be provided.
- Only one traffic type per ingress
                                        group is allowed.
- The configured traffic type
                                        must be removed before you configure a new traffic
                                        type.
- Both IPv4 and IPv6 addresses are
                                        supported.
- Valid IP addresses must be provided. The following IP addresses are not valid:
						- Unspecified IPv4 address
							(0.0.0.0)
- Broadcast IPv4 address
							(255.255.255.255)
- Unspecified IPv6 address
							(“::”)
- Broadcast IPv6 address
							(ffff:fffff:fffff:fffff:fffff:ffff:fffff:ffff)
 
- Existing traffic type cannot be
					configured again with a different ID, IP, or scope.
- The overlapping IP combination
                                        between different ingress-group traffic-type is not
                                        allowed.
- If the same command is run more
                                        than once, the second and subsequent instances are ignored
                                        and no error is reported.
- The no form of the
					command removes both traffic type and mode even if the mode is not
					specified.
Examples
			 
	  
		The following examples configures the ipip traffic
					type.
 
		device(config-ingress-group)# traffic-type ipip ip 192.168.2.1 255.255.255.0 192.168.3.2 255.255.255.0 
device# show ingress-group ing 
    Name : ing 
             Route-Map : - 
           Description : - 
            Interfaces : none 
          Traffic-Type : IPIP 
             Tunnel-Id : any 
                  Mode : none 
   Destination-ip-addr : 192.168.3.2 
   Destination-ip-mask : 255.255.255.0 
        Source-ip-addr : 192.168.2.1 
        Source-ip-mask : 255.255.255.0